| Package | hl7.ehrs.uv.phrsfmr2 |
| Resource Type | Requirements |
| Id | PHRSFMR2-PH.6.8 |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.6.8.html |
| URL | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.8 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_6_8_Manage_Patient_Specific_Care_and_Treatment_Plans |
| Title | PH.6.8 Manage Patient-Specific Care and Treatment Plans (Function) |
| Authority | hl7 |
| Description | The system should facilitate the capture and implementation of the care plan in the PHR-S. |
| Purpose | Once a care plan is developed it should be incorporated into the PHR-S. The care plan may be limited in scope or comprehensive involving multiple providers, encounters, institutions, and years of time. Example(s): A comprehensive breast cancer treatment plan may include multiple diagnostic imaging staging studies, surgical procedures, a chemotherapy protocol, details of the radiation therapy plan, plastic surgery reconstruction and long-term post therapy surveillance plan to be posted in the PHR-S and referenced by the cancer care team. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
The system should facilitate the capture and implementation of the care plan in the PHR-S.
Once a care plan is developed it should be incorporated into the PHR-S. The care plan may be limited in scope or comprehensive involving multiple providers, encounters, institutions, and years of time.
Example(s): A comprehensive breast cancer treatment plan may include multiple diagnostic imaging staging studies, surgical procedures, a chemotherapy protocol, details of the radiation therapy plan, plastic surgery reconstruction and long-term post therapy surveillance plan to be posted in the PHR-S and referenced by the cancer care team.
| PH.6.8#01 | SHOULD |
The system SHOULD provide the ability to capture PHR Account Holder-specific plans of care and treatment (e.g., information about orders or therapies). |
| PH.6.8#02 | SHOULD |
The system SHOULD provide the ability to capture updates to the PHR Account Holder's plan of care and treatment including authors, creation date, version history, references and sources as available. |
| PH.6.8#03 | MAY |
The system MAY provide the ability to capture adequate order details to promote the PHR Account Holder's understanding and compliance with the order. |
| PH.6.8#04 | SHOULD |
The system SHOULD provide the ability to present care and treatment plan recommendations in terms of the PHR Account Holder's health-related data (e.g., peak flow, weight, blood pressure, or dietary preferences) at the option or control of the PHR Account Holder or PHR Account Holder Proxy. |
| PH.6.8#05 | dependent SHOULD |
The system SHOULD provide the ability to transmit care plans, care instructions, treatment plans, guidelines, and protocols (or portions of those items) to selected stakeholders (e.g., sharing a new fitness plan with members of the care team, or sharing a care plan with a new member of the care team) according to user preference, organizational policy, and/or jurisdictional law. |
{
"resourceType": "Requirements",
"id": "PHRSFMR2-PH.6.8",
"meta": {
"profile": [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
}
],
"url": "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.6.8",
"version": "2.0.1-ballot",
"name": "PH_6_8_Manage_Patient_Specific_Care_and_Treatment_Plans",
"title": "PH.6.8 Manage Patient-Specific Care and Treatment Plans (Function)",
"status": "active",
"date": "2025-04-03T15:15:30+00:00",
"publisher": "EHR WG",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "The system should facilitate the capture and implementation of the care plan in the PHR-S.",
"purpose": "Once a care plan is developed it should be incorporated into the PHR-S. The care plan may be limited in scope or comprehensive involving multiple providers, encounters, institutions, and years of time.\r\n\r\nExample(s): A comprehensive breast cancer treatment plan may include multiple diagnostic imaging staging studies, surgical procedures, a chemotherapy protocol, details of the radiation therapy plan, plastic surgery reconstruction and long-term post therapy surveillance plan to be posted in the PHR-S and referenced by the cancer care team.",
"statement": [
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-PH.6.8-01",
"label": "PH.6.8#01",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture PHR Account Holder-specific plans of care and treatment (e.g., information about orders or therapies)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-PH.6.8-02",
"label": "PH.6.8#02",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture updates to the PHR Account Holder's plan of care and treatment including authors, creation date, version history, references and sources as available."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-PH.6.8-03",
"label": "PH.6.8#03",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "The system MAY provide the ability to capture adequate order details to promote the PHR Account Holder's understanding and compliance with the order."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-PH.6.8-04",
"label": "PH.6.8#04",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to present care and treatment plan recommendations in terms of the PHR Account Holder's health-related data (e.g., peak flow, weight, blood pressure, or dietary preferences) at the option or control of the PHR Account Holder or PHR Account Holder Proxy."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": true
}
],
"key": "PHRSFMR2-PH.6.8-05",
"label": "PH.6.8#05",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to transmit care plans, care instructions, treatment plans, guidelines, and protocols (or portions of those items) to selected stakeholders (e.g., sharing a new fitness plan with members of the care team, or sharing a care plan with a new member of the care team) according to user preference, organizational policy, and/or jurisdictional law."
}
]
}